Method and system for monitoring the health of wireless telecommunication networks

ABSTRACT

A method and system for monitoring the health of a wireless telecommunication network. Network health is monitored without placing an administrative burden on the carrier network itself, instead, this burden is placed on components that lie outside the carrier network and pass communications through it. The data service provider infrastructure sends a request to a mobile device, asking that it return data regarding its location. The carrier networks handling the request insert location information into the packet that is sent to the mobile device, but this information is not sent to the data service provider infrastructure itself. The mobile device harvests this location information from the packets it receives and inserts it in a response packet that finds its way back to the data service provider infrastructure. The data service provider infrastructure is able to collate this location data and to analyze it, determining the carrier network&#39;s health.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application is a Continuation of U.S. application Ser. No.10/995,062 filed Nov. 22, 2004, which claims priority from and isrelated to provisional patent application No. 60/561,582, filed on 13Apr. 2004, the contents of which are incorporated herein by reference.

This invention relates to communication networks, and more specifically,to a method and system for monitoring the health of wirelesstelecommunication networks.

BACKGROUND OF THE INVENTION

Over the last decade, digital communication networks employing personalcomputers (PCs), the Internet and other components, have increasedlevels of communication and access to information by an incredibledegree. In the beginning, most of these networks were effected usinghard-wired technology, but today, wireless digital services over GPRS(general packet radio service), CDMA (code division multiple access),Mobitex, DataTAC and similar systems are expanding the digitalcommunications and data access revolution in a mobile environment.Wireless email, digital paging and Internet browsing via portabledevices, for example, are now widely used.

Users of wireless telecommunication systems demand the very high levelsof reliability that they have became accustomed to from hard-wiredtelephone networks (often referred to as “five-9s” reliability—less thanone failure in 99,999 calls). However, administering a reliable wirelessdata service is much more difficult than hard-wired communications, notonly because wireless transmissions are more prone to noise andinterference, but also because many of the communications travel over anumber of disparate communication networks between the service providerand the end user, often including packet-switched networks such as theInternet, circuit-switched networks and wireless telecommunicationnetworks. While communications can move smoothly from one network toanother, the protocols necessary for more complex operability such asmonitoring network health are not standardized across such diversenetworks.

The monitoring and analysis of network health information is critical toimplementing reliable wireless data networks. As will be explained,existing systems do not facilitate effective network health monitoringand analysis.

An exemplary wireless data service network is presented in the simpleblock diagram of FIG. 1. In this example, a mobile node 10 is currentlybeing served by a carrier network 12A, which will include at least one,and probably multiple wireless base stations which are organized into“cells”; each cell covering a certain geographical area. The carriernetwork 12A may use both hard-wired and wireless communications toconnect these base stations and other infrastructure componentstogether. This carrier network 12A may even use frame relay networks,optical networks, the public switched telephone network (PSTN) and theInternet as part of its network.

The carrier network 12A generally serves as a conduit between the mobilenode 10 and the wireless data service provider infrastructure 14, simplypassing digital packets back and forth between these two parties,without considering the content of the packets themselves.

Because the mobile node 10 is mobile, it may pass from the region servedby one carrier network 12A, to another, such as carrier network 12B orcarrier network 12C. Methods are known in the art for “handing off”communications from one base station to another within a given carrier'sregion, or even handing communication off from one carrier to another.However, handoff situations make the health monitoring task far morecomplex as there is no standard for the collection and communication ofperformance data. The network of FIG. 1 is intended simply to present acontext for the problems in the art to be described. The details of acomplete implementation of the network would be clear to a skilledtechnician.

In addition to offering reliable systems, the stakeholders of thesewireless data networks want to optimize the use of their resources,offer cost effective services to their customers, and obtain someinsight into where future infrastructure investments can best be made.This can only be done if they have a detailed understanding of thetraffic flow and the performance of their network and networkcomponents.

Unfortunately, carrier networks are not designed to perform thecollection, collation and analysis of real time data that would benecessary to do this network health analysis. Even if special hardwareand software were added to the carrier networks 12A, 12B, 12C to performthe data analysis (in the form of servers, for example), the corenetwork nodes do not have the functionality to perform the collectionand collation tasks, for at least the following reasons:

1. Many of the nodes in these networks are designed to simply routedigital packets, so major software (and possibly hardware) changes wouldbe needed to provide the collection functionality;

2. Many of these nodes are optimized to perform their tasks as quicklyas possible, so that real time operation can be maintained. Providingthe extra functionality of analyzing network health may slow down theiroperation to an unacceptable level;

3. In some carrier networks, changing the functionality of the networknodes would require updating, testing and trouble shooting to beperformed on each node individually—an expensive and time consumingexercise; and

4. While some nodes in one carrier's network may be adaptable toperforming such functionality, it is unlikely that the whole networkwill. If the carrier uses a variety of networks and components includingwireless, hard-wired, fiber optic, PSTN, Internet, frame relay andpacket switched technologies, it may be impossible to obtain thenecessary data uniformly throughout the entire network to obtainmeaningful and useful data.

In other words, carrier networks are not in a position to obtain thenetwork health data that they desire.

There is therefore a need for an effective method and system ofcollecting network health information in wireless telecommunicationnetworks which avoids or addresses the problems outlined above.

SUMMARY OF THE INVENTION

It is an object of the invention to provide a method and system whichobviates or mitigates at least one of the disadvantages described above.

In accordance with an aspect of the present invention, a system isprovided for monitoring the health of a wireless telecommunicationnetwork, comprising: a mobile device; a data service providerinfrastructure; and a carrier network having a wireless connection tosaid mobile device and a connection to said data service providerinfrastructure; said data service provider infrastructure being operableto: generate a digital packet including a request for locationinformation; and transmit said request packet to said mobile device viasaid carrier network; said carrier network being operable to: receivesaid request packet from said data service provider infrastructure;attach location information for said mobile device, to said requestpacket; and transmit said request packet including said locationinformation, to said mobile device; and said mobile device beingoperable to: receive said request packet; extract said locationinformation from said request packet; insert said location informationinto a field of an acknowledgement packet that said carrier network willpass to said data service provider infrastructure; and return saidacknowledgement packet to said data service provider infrastructure, viasaid carrier network; said carrier network also being operable to:receive said acknowledgement packet from said mobile device; and passsaid acknowledgement packet to said data service providerinfrastructure; whereby said data service provider infrastructure mayuse said location information to analysis the health of saidtelecommunication network.

In accordance with another aspect of the invention, a method ofmonitoring the health of a wireless telecommunication network isprovided, said telecommunication network including at least one mobiledevice, a data service provider infrastructure and a carrier networkfacilitating communication between said mobile device and said dataservice provider infrastructure, said method comprising the steps of: atsaid data service provider infrastructure: generating a digital packetincluding a request for location information; and transmitting saidrequest packet to said mobile device via said carrier network; at saidcarrier network: receiving said request packet from said data serviceprovider infrastructure; attaching location information for said mobiledevice, to said request packet; and transmitting said request packetincluding said location information, to said mobile device; and at saidmobile device: receiving said request packet; extracting said locationinformation from said request packet; inserting said locationinformation into a field of an acknowledgement packet that said carriernetwork will pass to said data service provider infrastructure; andreturning said acknowledgement packet to said data service providerinfrastructure, via said carrier network; whereby said data serviceprovider infrastructure may use said location information to analysisthe health of said telecommunication network.

In accordance with a further aspect of the present invention, a serveris provided comprising: means for generating a packet requestinglocation information; means for transmitting the request packet to amobile device via a carrier network; means for receiving anacknowledgement packet from the mobile device; and means for extractinglocation information inserted into the acknowledgement packet by themobile device.

In accordance with an additional aspect of the invention, there isprovided a mobile device comprising: means for receiving a requestpacket, initiated by a data service provider infrastructure; means forextracting location information from the request packet, the locationinformation having been added to the request packet by a carriernetwork; means for inserting the location information into a field of anacknowledgement packet that the carrier network will pass to the dataservice provider infrastructure; and means for returning theacknowledgement packet to the data service provider infrastructure, viathe carrier network.

Other aspects and features of the present invention will be readilyapparent to those skilled in the art from the following detaileddescription of preferred embodiments in conjunction with theaccompanying drawings.

BRIEF DESCRIPTION OF THE DRAWINGS

These and other features of the invention will become more apparent fromthe following description in which reference is made to the appendeddrawings in which:

FIG. 1 presents a block diagram of an exemplary network architecture towhich the invention may be applied;

FIG. 2 presents a flow diagram of a method of monitoring network health,in an embodiment of the invention;

FIG. 3 presents a block diagram of an exemplary server architecture inan embodiment of the invention;

FIG. 4 presents a block diagram of an exemplary mobile device, in anembodiment of the invention;

FIG. 5 presents a block diagram of an exemplary network architecture, inan embodiment of the invention; and

FIG. 6 presents a flow diagram of a method of monitoring network health,in an embodiment of the invention.

DESCRIPTION OF THE INVENTION

The invention allows network health to be monitored without placing anadministrative burden on the carrier network itself. This is done byplacing this burden on components that lie outside the carrier network,passing communications through it. The invention is suited for manynetwork architectures and can be, for example, applied to that of FIG.1.

Broadly speaking, the method of the invention is effected as shown inthe flow diagram of FIG. 2. This process begins at step 20, by havingthe data service provider infrastructure 14 send a request to the mobiledevice 10 of the end user, via one of the carrier networks 12A, 12B, 12Casking that it return data regarding its location. The carrier networks12A, 12B, 12C cannot distinguish these instructions from any otherdigital packet transmitted by the data service provider infrastructure14, so they simply pass the request packet to the mobile device 10 atstep 22 (techniques for performing basic communications are known in theart and will not be described herein).

However, in passing the request packet, the carrier networks 12A, 12B,12C will add location data to the packet. This is a standard procedurein wireless communications as the location data is generally insertedinto the header of each packet at step 22, for identification andbook-keeping purposes.

The mobile device 10 receives the request packet and extracts the dataregarding its location at step 24. The location data is entered into afield of an acknowledgement packet at step 26 and is sent to the carriernetwork 12A, 12B, 12C. The carrier network 12A, 12B, 12C will simplypass any packets that it receives, back to the data service providerinfrastructure 14 at step 28.

Receiving location data from all mobile devices, the data serviceprovider infrastructure 14 is able to collate the data and analyze it atstep 30 to obtain an overall picture of the telecommunication system'shealth including the operability of the various carrier networks 12A,12B, 12C.

The nature of the location data is described in greater detailhereinafter with respect to the preferred embodiment of the invention,but could include, for example, the identity of the carrier network'sbase station serving the mobile device 10. This data alone would providea great deal of information as it would locate each end user's positionwithin several kilometers. The routing of the communication through theresources of the carrier's network 12A, 12B, 12C could then bedetermined.

This location data could, for example, be used to calculate peak demandlevels per base station, the variance of traffic levels with respect tothe hour of the day, or average levels of traffic by geographic area.Other analyses known in the art of telecommunication resources andtraffic management could also be performed, some of which are describedhereinafter.

As noted above, the digital data may be communicated using many systemsknown in the art, including: GPRS, CDMA, Mobitex and DataTAC systems. Astime passes, surely other wireless data protocols and technologies willalso evolve; the invention is equally applicable to such protocols andtechnologies as it operates independently of features of the carrier'snetwork. Also, the mobile devices used by the end user could be one ofmany known in the art, including digital cellular telephones, personaldigital assistants (PDAs), wireless laptop computers, wearable computersor two-way pagers. The invention is not limited by the nature of themobile device to which it is applied.

The invention is also not limited by the nature of the digital packetsbeing employed. That is, while FIG. 2 suggests that specific pairings oflocation “request” packets and “acknowledgment” packets will beemployed, requests for location data and the location data itself willgenerally be combined with other packets. In the preferred embodimentdescribed hereinafter, for example, requests for location data are madesimply by setting a single bit in a generic digital packet. Similarly,location data is returned by piggy-backing it on another packet thatwould be sent as part of the existing protocol. Hence, any control ordata packet could be used to carry location requests or location data.

The data service provider's system may be quite complex, including, forexample, a number of nodes or servers, geographically distributed andinterconnected via some communication network such as the Internet. Atthe other extreme, the data service provider infrastructure 14 maycomprise just a single server—in such a case, the functionality of theserver could be implemented, for example, in the hardware format shownin FIG. 3.

As shown in the block diagram of FIG. 3, the data service provideinfrastructure 14 may be embodied as a server consisting of three maincomponents: a receiver/transmitter 40 that receives and transmits dataand/or control packets to and from various carrier networks, in themanner known in the art; a data processor 42 that is operable to performa large number of tasks, including the following: generating packets ormodifying packets to ask the mobile device to forward location data (the“request packets”); extracting location data from received packets; andcollating and/or analyzing the collected location data (note that thistask could also be deferred to another device); and a database 44 forstoring location data as it is received. Note that this component couldbe internal to the server, or external. The storage technology usedcould take on any form, limited only by the access speed and storagecapacity that is required for a particular application.

As noted above, the mobile device 10 of the invention takes on any ofmany forms, including cellular telephones, personal digital assistants(PDAs), wireless laptop computers, wearable computers or two-way pagers.A generic mobile device 10 is presented in the block diagram of FIG. 4.

At the heart of this device lies a central controller 62 which may, forexample, be a digital signal processor (DSP), microprocessor,microcontroller or ASIC (application specific integrated circuit). Thiscontroller 62 performs the basic functionality of the invention for themobile device 10.

The interface components of the mobile device 10 will vary with theapplication. For example, in cellular telephone applications, an audioinput and output 60 may be included, as well as signal processingcomponents such as analogue to digital and digital to analogueconverters, to pass voice signals to and from the central controller 62.As well, a cellular telephone may include a manual input interface 64 inthe form of a mechanical keypad, and a display 66 consisting of a simpleliquid crystal display (LCD) with a single line of alphanumericcharacters to present dialed numbers and other information.

A wireless PDA, on the other hand may not have an audio interface 60,but may have much more comprehensive manual and visual interfaces. Thedisplay 66, for example, could comprise an LCD pixel matrix which coulddisplay graphics as well as alphanumerics. Rather than a traditionaltelephone keypad, the manual input interface 64 could comprise a mouseand pushbutton which drives a cursor on the display 66, allowing theuser to select icons in a graphic user interface (GUI) to executedesired functions.

All of these mobile devices 10 will also include some manner of wirelesstransmission and reception components 68, as known in the art.

The controller 62 will also generally have access to off-processormemory 70, though it is possible that all necessary memory could beincluded on chip with the controller 62. Such memory could be anon-volatile memory such as an electrically erasable programmable readonly memory (EEPROM) or FlashROM, but may also be a volatile memory suchas a random access memory (RAM). This memory 70 may be used to storeuser data, operating data or operating algorithms.

The controller 62 will execute some form of communication algorithm, andin the context of the invention, also have the functionality to performthe following tasks: receiving request packets; extracting locationinformation from received packets; generating acknowledgement packetsand inserting location information into such acknowledgement packets;and returning acknowledgement packets to the data service providerinfrastructure 14, via a carrier network 12A, 12B, 12C. Thisfunctionality could easily be added to existing mobile devices 10, withsimple alterations to their existing software code.

The implementation of the invention provides many advantages to theoperators of the various networks. For example, it allows the carriernetwork 12A, 12B, 12C to: determine how heavy the loading is on itsresources, and what the traffic patterns are; identify heavy load areas,which allows it to concentrate its upgrade efforts in areas that willprovide the best return on investment; detect performance problems, forexample, if a certain base station can be found to be operating at lessthan expected capacity (or not at all); and the invention can beimplemented without carriers having to change any hardware or softwareon their systems.

The invention also provides many benefits to the digital serviceprovider 14, for example: it can determine whether a service problemlies with the data service provider infrastructure 14 or with acarrier's network 12A, 12B, 12C, so end user complaints can be directedto the particular party responsible for the problem. This reduces helpdesk costs and increases user satisfaction; it can determine how quicklymessages are circulating through the network. This may assist indetermining whether a carrier 12A, 12B, 12C is handling messages asquickly as it is supposed to. The data is collected by time stamping“request” packets as they depart from the digital service providerinfrastructure 14, and comparing that with the time at which acorresponding “acknowledgement” packet is returned; and it gives thedigital service provider 14 an additional service which can be offeredto the carriers 12A, 12B, 12C. This might become a market differentiatorbetween different digital service providers. Also, because of where thenew functionality is located (at the mobile devices 10 and at the dataservice provider infrastructure 14), it is easy to upgrade software asrequired. Additional advantages of the invention are describedhereinafter with respect to the preferred embodiments of the invention.

Preferred Embodiments of the Invention

One of the parameters that drives the preferred embodiment of theinvention is that of privacy. Regulations regarding the privacy of endusers vary from one legal jurisdiction to another, and in fact, desiredprivacy levels may vary from one customer to another (some companies,for example, may demand higher levels of security than the levelsrequired by law). Accordingly, it is generally necessary to implementthe invention with the following limitation: requiring that locationinformation and end user's equipment identifiers never be storedtogether in a permanent database. However, this restriction means thatmobile devices cannot be tracked as they move, and as a result onecannot maintain mobile device population and density statistics fornetwork base stations.

There are also a number of other restrictions that it is desirable tosatisfy. For example: it is preferable that mobile devices and serversimplementing the invention be backwards compatible with earlier versionsof these components. This is desirable from a business standpoint as itwould allow the same infrastructure to support both versions of theequipment; power consumption of mobile devices is very important. Thus,it is preferable to minimize the number of additional data transmissionsthat will have to be performed, and to minimize the number of additionalbits required in those transmissions.

The system architecture of the preferred embodiment is much like that ofFIG. 1, except that as shown in FIG. 5, the data service providerinfrastructure 14 preferably consists of a server 80 connected tovarious carrier networks 12A, 12B, 12C via an Internet network 82 and agateway 84. This allows a single server 80 (or cluster of servers) tomanage many end users and carrier networks 12A, 12B, 12C over a broadgeographic area. The architecture of FIG. 5 also explicitly shows a basestation 86 that provides the wireless link to the mobile device 10.

The message flow diagram of FIG. 6 presents the preferred method of theinvention. In fact, FIG. 6 presents only part of a regularcommunication, focusing on the communications that deal with thetransfer of location data specifically.

To begin with, a communication link is established between the server 80and the mobile device 10, via the intermediate components (specifically,the Internet network 82, gateway 84, carrier network 12A and basestation 86). The manner in which this communication is established iswell known in the art, and will vary with the particular communicationsystem and protocol being employed.

At some point after this communication link has been established, thealgorithm on the server 80 will decide that location information isneeded, and a control or data packet will issue, including a request forlocation information. This packet will be transmitted to the mobiledevice 10 at step 100. In the preferred embodiment of the invention anycontrol of data packet may be used, with a single bit set as a flag,which indicates to the mobile device 10 that location information isdesired.

In the preferred embodiment, the request packet that is being sent, is apacket that would be sent in the usual course of communication betweenthe enterprise server 50 and the mobile device 10. Thus, theimplementation of the invention does not increase the number of messagesbeing sent between the enterprise server 50 and the mobile device 10. Aswell, by using only a single bit as the flag to indicate that locationinformation is desired, there is only a very small increase in theamount of bandwidth and power needed to transmit this packet.

The bit that is set is not used in regular communications, thus theimplementation of the invention is backwards compatible to mobiledevices that are not equipped to handle the invention. Older versions ofmobile devices will simply ignore the setting of this unused bit.

This request packet is then routed through the rest of the data serviceprovider's infrastructure (Internet network 82 and gateway 84), in themanner know in the art.

The carrier network 12A then receives the request packet at step 102,and attaches location data to it at step 104, passing it on to themobile device 10. As noted above, this location data is used by thecarrier network 12A and mobile device 10 for book keeping purposes.

Ultimately, this request packet is received by the mobile device 10, andis examined at step 106 for the presence of the bit which indicates thatlocation data is required. As noted above, mobile devices that are notcompatible with the invention, will ignore the setting of this bit as itis unused. Such non-compatible mobile devices will then prepare astandard acknowledgement packet, and return that packet to the server80. This allows the invention to be backward compatible with oldersystems.

Mobile devices 10 that are compatible with the invention will alsoprepare an acknowledgement packet in response, but will extract thelocation data from the received request packet at step 108, store itlocally, and then insert it into the acknowledgement packet at step 110.As in the case of the request packet above, no additional packets havebeen added to the standard communication flow, minimizing the impact ofthe invention on power consumption and bandwidth.

The location data that is inserted into the acknowledgement packet willvary with the application, but may include one or more of the followingparameters. Note that this location information is formatted in theacknowledgement packet as a sequence of tag/length/value. In the valuefield, the data related to the value on the tag field is entered, whilethe length filed is used for entering the length of the data. The tagsmay be defined as follows:

Tag=1 (NPC—1, 4 or 8 bytes)Tag=2 (Country code), a standard telecommunications code that identifiesthe country is which the mobile device 10 is being used;Tag=3 (Network code);Tag=4 (Location area);Tag=5 (Routing area);

Tag=6 (Base); Tag=7 (Area); Tag=8 (Channel); Tag=9 (TrafNum);

This location data is simply inserted into a field of theacknowledgement packet that the carrier network 12A will regard as datarather than instructions to it; thus, the carrier network 12A willsimply pass this location information back to the server 80 at step 112.

When the server 80 receives the acknowledgement packet at step 114, itdetermines whether location data has been included, by virtue of whetherone or more location data fields have been filled. If so, the locationdata is stored, collated and/or analyzed at step 116.

This process of sending requests and receiving acknowledgementsincluding location data, can be executed on a continuous basis, so thatthe system's understanding of network health stays current. That is, themobile device 10 could return location data in response to any packetreceived from the server 80.

As noted above, many traffic management and network analysis techniquesare known in the art. These would include the following: determiningaverage and peak packet delivery times and related those times toparticular base stations or carrier networks; determining base stationtraffic patterns such as packet delivery rates, packets/minute/base, anddelivery round-trip/base; predicting traffic problems due to statisticalincreases in demands on certain network nodes; and determining thenumber of mobile devices connected to a particular carrier or basestation with respect to time of day.

Other Privacy Issues

As noted above, regulatory requirements regarding the privacy of endusers may vary from one legal jurisdiction to another, and may even varyfrom one customer to another. In general, however, they do not allowlocation information and the end user's equipment identifiers to bestored together in a permanent database.

As well, it may be desirable to implement the invention with thefollowing functionality, in the interest of privacy: mobile devices mayimplement an option whereby the end user can disable the reporting oflocation information. This is easily done by having mobile devicesignore the request for information; IT Policy may be extended to allowan IT department to disable the reporting of location information forany of its end users; and licensing agreements may be amended to includea paragraph informing the customer that the data service provider maycollect mobile device location. All of these options are easilyimplemented in view of the description of the invention above.

Other Considerations

The details of how the invention could be applied to differentenvironments will vary. However, a number of other importantconsiderations include the following:

1. Device Presence Reports: While avoiding privacy information, it stillmay be desirable to monitor the approximate number of mobile devices andtheir ability to communicate with the network. If ping packets (forexample, the GCMP ping sent in the case of GPRS and CDMA, every 15minutes), were replaced with packets that include location information,then one could maintain a count of device reports per minute per base.Note that ping packets are not generally sent if there is regularcommunication with a mobile device, so replacing ping packets with alocation report does not guarantee that all mobile devices will alwayssend the reports. However, when the location reports are combined withdelivery acknowledgements containing location information, there will besufficient information to determine network performance trends, and tomake a better determination of base station health;

2. Use of Send-only Devices: If a device only sends messages, and neverreceives messages, then it will never send location information. If toomany such devices are present then the statistical information gatheredthrough the location reports will be inaccurate. It is assumed, though,that the percentage of devices which only send messages will be verysmall, and thus have little impact; and

3. Opt-out Devices: Since it is desirable to provide methods which allowmobile devices to opt out of reporting their locations, the statisticalinformation will be inaccurate according to the percentage of deviceswhich opt out of these reports.

CONCLUSIONS

Numerous modifications, validations and adaptations may be made to theparticular embodiments of the invention described herein, withoutdeparting from the scope of the invention, which is defined in theclaims.

While particular embodiments of the present invention have been shownand described, it is clear that changes and modifications may be made tosuch embodiments without departing from the true scope and spirit of theinvention. For example, the invention could be applied to digital oranalogue communications, or voice or data, using wireless, fiber opticor hardwired technologies.

The method steps of the invention may be embodiment in sets ofexecutable machine code stored in a variety of formats such as objectcode or source code. Such code is described generically herein asprogramming code, or a computer program for simplification. Clearly, theexecutable machine code may be integrated with the code of otherprograms, implemented as subroutines, by external program calls or byother techniques as known in the art.

The embodiments of the invention may be executed by a computer processoror similar device programmed in the manner of method steps, or may beexecuted by an electronic system which is provided with means forexecuting these steps. Similarly, an electronic memory medium suchcomputer diskettes, CD-ROMs, Random Access Memory (RAM), Read OnlyMemory (ROM) or similar computer software storage media known in theart, may be programmed to execute such method steps. As well, electronicsignals representing these method steps may also be transmitted via acommunication network.

1. An apparatus for facilitating monitoring of the health of atelecommunication network, said apparatus comprising: a requestgenerator configured to generate a request for mobile-device locationinformation; an identifier configured to identify location datacontained in a response to the request generated by said requestgenerator; and an analyzer configured to analyze the location dataidentified by said identifier, analysis of the location data providingindication of the health of the telecommunication network.
 2. Theapparatus of claim 1 further comprising a data service providerinfrastructure device connected to, and separate from, thetelecommunications network.
 3. The apparatus of claim 1 wherein therequest generated by said request generator comprises a flag of a packetmessage.
 4. The apparatus of claim 3 wherein said request generator isconfigured to use a single bit as the flag.
 5. The apparatus of claim 1wherein the location data contained in the response and identified bysaid identifier comprises a field of an acknowledgement packet.
 6. Theapparatus of claim 5 wherein the field of the acknowledgement packetcontaining the location data comprises a data field.
 7. The apparatus ofclaim 1 wherein said identifier is further configured to determinewhether the response includes the location data.
 8. The method forfacilitating monitoring of the health of a telecommunication network,said method comprising: generating a request for mobile-device locationinformation; identifying location data contained in a response to therequest generated during said generating; and analyzing the locationdata identified during said identifying, analysis of the location dataproviding indication of the health of the telecommunication network. 9.The method of claim 8 wherein said generating, said identifying, andsaid analyzing are performed at a data service provider infrastructuredevice connected to, and separate from, the telecommunications network.10. The method of claim 8 wherein said generating the request comprisesgenerating a flag of a packet message.
 11. The method of claim 10wherein the flag comprises a single bit.
 12. The method of claim 10wherein the flag comprises a single bet of the packet message.
 13. Theapparatus of claim 8 wherein the location data contained in the responseidentified during said identifying comprises a field of anacknowledgement packet.
 14. The apparatus of claim 8 wherein saididentifying further identifies whether the response includes thelocation data.
 15. An apparatus embodied at a mobile device forfacilitating monitoring of the health of a telecommunication network,said network comprising: an examiner configured to examine a receivedpacket to determine whether the received packet includes a request forlocation data of the mobile device; an extractor configured to extractlocation data from the received packet if said examiner determines thatthe received packet includes the request for the location information;and an inserter configured to insert the location information into anacknowledgment packet.
 16. The apparatus of claim 15 wherein saidexaminer is configured to examiner a flag of a received packet todetermine whether the received packet includes the request for thelocation data.
 17. The apparatus of claim 15 wherein the location dataextracted by said extractor comprises network-added location data.
 18. Amethod at a mobile device for facilitating monitoring of the health of atelecommunication network, said method comprising: examining a receivedpacket to determine whether the received packet includes a request forlocation information of the mobile device; extracting location data fromthe received packet if determination is made during said determiningthat the received packet includes the request for the locationinformation; and inserting the location information into anacknowledgement packet.
 19. The method of claim 18 wherein saidexamining comprises examining a single-bit flag of the received packetto determine whether the received packet includes the request furtherlocation information.
 20. The method of claim 18 wherein said extractinglocation data comprises extracting network-added location data from thereceived packet.